Setup overview

Figure 1 illustrates our system setup.

Figure 1. Diagram of the setup



NOTE: All machines used for this study were Microsoft® Windows® Server 2008 Standard, 64 bit.

Installing IBM DB2®

First, we need to install IBM DB2, using the following steps:

1. Run the installer (launchpad.exe), and select “Install IBM DB2” from the left-hand menu bar (see figure 2).
2. Click the Install IBM DB2 link.

Figure 2. Welcome screen



3. If IBM Installation Manager is not already installed on the machine, you will be prompted to install it (see figure 3).

Figure 3. IBM Installation Manager window



4. Click the next button on each screen, accepting the license agreement, choosing the defaults values every time, and then click install.
5. Once installed, click Restart Installation Manager.
6. Once restarted, click install, and select DB2 Version 9.7.0.0, as shown in figure 4; click Next.

Figure 4. Installation Packages window



7. Accept the terms in the license agreement; click Next.
8. Choose the default Shared Resources Directory; click Next.
9. Accept the Create New Package Group default settings; click Next.
10. Click Next on the Install Package screen, leaving the default settings.
11. Enter a db2admin password and click Next (see figure 5); then click Install.

Figure 5. DB2 credentials window

Installing the Sametime System Console

Before starting the install of the System Console, you must copy the database creation files from the System Console installation folder to the DB2 machine. Copy the folder called “DatabaseScripts” in SSC\setup\SSCLP\disk1 to the location to which you have downloaded the System Console build.

1. Create the database needed for the system console:
2. On your system console machine, kick off the installer (launchpad.exe).
3. Choose Install IBM System Console from the left-hand menu (see figure 6).
4. Click the “Launch IBM Lotus Sametime System Console 8.5.1 Installation” link.

Figure 6. Welcome screen



5. As with the DB2 installation, if IBM Installation Manager is not already installed, you will be prompted to install it first. Use the same steps as in the “Installing IBM DB2” section above.
6. When Installation Manager has started, choose Install, select “IBM Sametime System Console server,” and click Next (see figure 7).

Figure 7. Installation Packages window



7. Accept the license terms; click Next. Click Next on the Install Packages screen, accepting the default settings.
8. Click Next on the Create New Package Group screen, accepting the default settings. Click Next on the Installation screen.
9. Choose to “Use Sametime installed WebSphere Application Server” and click Next.
10. On the WebSphere Application Server (WAS) configuration screen, just enter the WAS password you want to use and click Next (see figure 8).

Figure 8. WAS Configuration window



11. On the next window (see figure 9), enter your DB2 settings. Note that, when entering the DB2 host name, you must use the fully qualified domain name. For the database name, use whatever you entered on the DB2 machine when you ran the createSCDb.bat file.

Figure 9. DB2 properties window


12. Click the Validate button and, when validated, click Next. Finally, click Install.

Installing IBM Lotus® Domino®

To install the Domino server:

1. Run the installer for Lotus Domino, choosing the default folder to save files (see figure 10); click Next.

Figure 10. Default folder to save files



2. Click Next on the Installation screen and accept the license terms.
3. Accept the default Program Files Directory Name; click Next. Accept the default Data Files Directory Name; click Next.
4. Select Domino Enterprise Server as your setup type; click Next (see figure 11).

Figure 11. Domino Enterprise Server option



5. Click Next to start installing; then click Finish to exit the wizard.

Setting up Lotus Domino

After the Domino installation completes, you must set it up, as follows:

1. Launch the Domino application; you will be asked to follow steps to set it up (see figure 12). Click Next.

Figure 12. Set up a new Domino server


2. Select the option, “Set up the first server or a stand-alone server”; click Next (see figure 13).

Figure 13. Set up a new Domino server



3. In the next window, enter your server name and title (optional); click Next (see figure 14).

Figure 14. Server name and title



4. Just enter your password on the next window and click Next (see figure 15).

Figure 15. Password window



5. Accept the default Domino domain name in the next screen and click Next.
6. Enter an admin password and enable (place a check mark) the option, “Also save a local copy of the ID file”; click Next (see figure 16).

Figure 16. Admin password



7. Just select the Web Browsers (HTTP services) option and click Next (see figure 17).

Figure 17. “Setup Internet services for” window



8. Make sure your Host name is correct on the Domino network settings window (see figure 18). Click Next.

Figure 18. Domino network settings window



9. Click Next again, on the Secure your Domino Server window (see figure 19).

Figure 19. Secure your Domino Server window



10. Click Setup to start the setup of Lotus Domino; finally, click Finish to close the setup.

NOTE: Select Control Panel – Administrative Tools – Services, to locate the Lotus Domino service. Click on the service and in the drop-down menu for “Startup type” set it to “manual.” Apply and click OK. This way you can control the startup and shutdown of the Domino server.

Connecting to LDAP

The next step is to connect to the LDAP directory. This can be done once the System Console has been installed. In our configuration we use a Microsoft Active Directory.

1. Enter the following into a Web browser:

System_Console_Server:8700/ibm/console, for example:



2. Log in with your wasadmin credentials.
3. From the drop-down list on the left-hand menu bar, select Sametime System Console (see figure 20) and, under that, expand the Sametime System Console option.

Figure 20. Sametime System Console option


4. Expand Sametime Prerequisites and select “Connect to LDAP Servers” (see figure 21).

Figure 21. Sametime Prerequisites expanded


5. Click the Add button, as shown in figure 22.

Figure 22. Connect to LDAP server


6. Enter your LDAP details and click Next; for example, figure 23 shows the details we used.

Figure 23. Bind to LDAP window



7. In the next window, enter your correct LDAP base distinguished name and filter for searches; click Next (see figure 24).

Figure 24. Base Distinguished Name and Filter for Searches window


8. Verify your summary information and click Finish (see figure 25).

Figure 25. Task Completion Summary window


You should then see your LDAP server listed in the LDAP list (see figure 26). Note that changes will not take effect until the Deployment Manager has been restarted.

Figure 26. Connect to LDAP Servers window

Installing the Sametime Community server

1. After you have restarted the Deployment Manager, log back into it in a browser, (http://<system_console_machine>:8700/ibm/console), using your wasadmin credentials.
2. Choose Sametime System Console from the drop-down menu on the left-hand side and expand Sametime Guided Activities (see figure 27).

Figure 27. Sametime Guided Activities expanded



3. Select the Install Sametime Community Server option.
4. Select “Create a new deployment plan,” click Next, give it a deployment name, and click Next again.
5. Select version 8.5.2; click Next. Enter your Domino server details (see figure 28) and click Next, making sure Lotus Domino is running.

Figure 28. Connect to Domino Server window



6. Select the “Use the Sametime Server” option in the Slide Conversion window; click Next (see figure 29).

Figure 29. Slide Conversion window


7. Select your LDAP and click Next (see figure 30).

Figure 30. Connect to an LDAP Server window


8. On the next window (see figure 31), do not check the “Enable HTTP tunneling” option; click Next.

Figure 31. HTTP Tunneling window


9. Verify your summary information and click Finish (see figure 32).

Figure 32. Deployment Summary window



You should now see your plan:

Install steps

1. Log in to your Domino server and stop the server by issuing the “quit” command on the console.
2. Kick off the installer for your Sametime Community Server, click Next to start the installation process, and accept the license terms.
3. Select Yes to “Use the Sametime System Console?”; click Next (see figure 33).

Figure 33. Use the Sametime System Console



4. Enter the details about your system console and click Next (see figure 34).

Figure 34. Sametime System console details window



5. Select your deployment plan and click Next (see figure 35).

Figure 35. Select deployment plan



6. Click Install to start the installation; click Finish to close the setup.

Installing the Sametime Meeting Server

You must first create the database for the Meeting Server on your DB2 machine. To do this:

1. Copy the folder called ‘DatabaseScripts’ located in MS\setup\ST85MSLaunchpad\disk1 in the location to which you have downloaded the Meeting Server build.
2. Go to the command line on your DB2 machine (make sure you are logged into the OS as the db2admin user) and navigate to the directory in which you have copied the Meeting server database creation files.
3. Run the batch file like so:



4. Go to your system console in a browser:

5. Log in using your wasadmin credentials. Select “Sametime System Console” from the drop-down menu and expand “Sametime Prerequisites.”
6. Click “Connect to DB2 database”, and add the database you just created above, using the createMeeting batch file. You will need to enter the name of your DB2 machine, the database name, and the db2admin username and password.
7. Once connected, you should see the database you just created, as well as the Sametime System Console database (SSCDB) you created earlier (see figure 36).

Figure 36. SSCDB



8. Now, select “Sametime System Console” from the drop-down menu and expand “Sametime Guided Activities” (see figure 37).

Figure 37. Sametime Guided Activities



9. Click “Install Sametime Meeting Server” and choose “Create a new development plan”; click Next.
10. Enter a name for your plan and click Next. Choose the product version 8.5.2 and click Next.
11. Choose “Cell” configuration or “Primary Node” configuration, depending on the deployment type you want, and click Next.

12. Enter your Meeting server host name, the wasadmin user name, and the password you want to use; click Next.
13. Choose your database for your deployment, making sure to choose the one you made for Meeting Server; click Next (see figure 38).

Figure 38. Choose a database for this deployment


14. Choose your LDAP and click Next.
15. Review your summary information and click Finish.

Install steps

1. Now, log in to your Meeting Server machine and kick off the installer for the Meeting Server. Again, if IBM Installation Manager is not installed, it will prompt you to install that first.
2. Click Install, to install the Meeting server; select the Sametime Meetings server package, and click Next.

Figure 39. Sametime Meetings server package


3. Accept the license terms and click Next. Accept the default install directory and click Next.
4. Select “Create a new package group”, use the default settings, and then click Next.
5. Select “Use Lotus Sametime System Console to install” and click Next:

Figure 40. Use Lotus Sametime System Console to install


6. Select to “Use Sametime installed WebSphere Application server” and click Next.
7. Enter the system console server details and click Validate (see figure 41).

Figure 41. System Console server information


8. Once validated, click Next, choose the meeting plan you set up, and click Next.
9. Verify your deployment plan and click Next.
10. Click Install to install; click Finish to close the installer.

Installing the Sametime Proxy server

1. Go to your system console in a browser, @nowiki@5and log in using your wasadmin credentials.
2. Select “Sametime System Console” from the drop-down menu and expand “Sametime Guided Activities”.
3. Click “Install Sametime Proxy Server” and choose to create a new deployment plan; click Next.
4. Name your plan and click Next. Choose version 8.5.2 and click Next.
5. Choose “Cell” configuration or “Primary Node” configuration, depending on the deployment type you want, and click Next.

6. Enter your Proxy Server host name, and the wasadmin user name and password you want to use.
7. Select your Community Server; click Next. Verify your summary information and click Finish (see figure 42).

Figure 42. Proxy server deployment summary

Install steps

1. Now, go to your Proxy server and kick off the installer. Again, if IBM Installation Manager is not installed, it will prompt you to install that first.
2. Click Install to install the Proxy server, choose the Proxy server package, and click Next (see figure 43).

Figure 43. Sametime Proxy server


3. Accept the license terms and click Next. Accept the default install directory and click Next.
4. Use the default settings on Create new group and click Next.
5. Choose “Use Lotus Sametime System Console to install” and click Next

Figure 44. Use Lotus Sametime System Console to install


6. Choose “Use Sametime installed WebSphere Application Server” and click Next.
7. Enter your System Console information and click Next (see figure 45).

Figure 45. System Console server information


8. Once validated, click Next. Choose your plan and click Next.
9. Verify your plan and click Next. Click Install; click Finish to close the setup.

Installing the Media Server

1. Go to your system console in a browser, <name_of_system_console_server>:8700/ibm/console, and log in using your wasadmin credentials.
2. Select Sametime System Console from the drop-down menu and expand “Sametime Guided Activities.”
3. Click “Install Sametime Media Manager” and choose to create a new deployment plan; click Next.
4. Enter a deployment name and click Next. Choose product version 8.5.2 and click Next.
5. Choose Install All Components, and click Next (see figure 46).

Figure 46. Media Manager Feature Installation window



6. Choose “Cell” configuration or “Primary Node” configuration, depending on the deployment type you wish to have and click Next (see figure 47). Note that Cell means the server will have its own deployment manager on the same box, whereas Primary Node means it will use the System Console as its deployment manager.

Figure 47. Choose configuration type


7. Fill in the details of your AV (Media Manager) server and click Next (see figure 48).

Figure 48. Media Manager server details


8. Choose your Community Server (cs) and click Next (see figure 49).

Figure 49. Choose Community Server


9. Verify your summary information and click Finish.

Install steps

1. Now, go to your AV server and kick off the AV installer. Again, if IBM Installation manager is not installed, it will prompt you to install that first.
2. Click Install to install the AV server. Choose the Sametime Media server package and click Next (see figure 50).

Figure 50. Sametime Media server


3. Accept the license terms and click Next. Accept the default directory and click Next.
4. Accept the defaults for “Create a new package group” and click Next.
5. Choose “Use Lotus Sametime System Console to install” and click Next (see figure 51).

Figure 51. Use Lotus Sametime System Console to install


6. Choose to “Use Sametime installed WebSphere Application Server” and click Next.
7. Enter your System Console details and click Validate (see figure 52).

Figure 52. System Console server details


8. Once validated, click Next. Choose your deployment plan and click Next.
9. Verify your deployment details and click Next.
10. Click Install to start the installation, and click Finish to close the setup.
11. Log in to your Domino server machine and locate the Sametime.ini file (if you installed to the default location, it should be in C:\Program Files (x86)\IBM\Lotus\Domino).
12. Edit the file, and under the [Debug] heading, add the following line:

For example:


13. Restart the Community server.

Installing the Sametime Advanced server

You must first create the database for the Advanced server on your DB2 machine. To do this:

1. Copy the folder called "DatabaseScripts" located in AS\setup\STAdvancedLaunchpad\disk1\ to the location to which you have downloaded the Advanced Server build.
2. Go to the command line on your DB2 machine (make sure you are logged into the OS as the db2admin user) and navigate to the directory in which you have copied the Meeting server database creation files.
3. Run the batch file, createAdvancedDb.bat <DatabaseName> <DbUserName>; for example:



4. Go to your System Console in a browser:

5. Log in using your wasadmin credentials. Select “Sametime System Console” from the drop-down menu and expand “Sametime Prerequisites.”
6. Click “Connect to DB2 database”, and add the database you just created above, using the createAdvancedDb batch file. You will need to enter the name of your DB2 machine, the database name, and the db2admin username and password.
7. Once connected, you should see the database you just created, as well as the System Console database (SSCDB) you created earlier (see figure 53).

Figure 53. SSCDB



8. Now, select “Sametime System Console” from the drop-down menu, and expand “Sametime Guided Activities” (see figure 54).

Figure 54. Sametime Guided Activities



9. Click “Install Sametime Advanced Server”, choose “Create a new development plan”; click Next. Enter a name for your plan and click Next.
10. Choose “Cell” configuration or “Primary Node” configuration, depending on the deployment type you want, and click Next. Note that Cell means the server will have its own deployment manager on the same box, whereas Primary Node means it will use the System Console as its deployment manager.
11. Enter your Advanced Server host name, the wasadmin user name, and the password you want to use; click Next.
12. Tick the box to “Use the WebSphere Administrator” credentials.
13. Choose your database for your deployment, making sure to choose the one you made for Advanced server, and click Next (see figure 55).

Figure 55. Choose a database for this deployment


14. Choose your LDAP and click Next. Review your summary information and click Finish.

Install steps

1. Now, log in to your Advanced Server machine and kick off the installer for the Advanced server. Again, if IBM Installation Manager is not installed, it will prompt you to install that first.
2. Click Install, to install the Advanced server, select the Sametime Advanced server package, and click Next (see figure 56).

Figure 56. Sametime Advanced server


3. Accept the license terms and click Next. Accept the default install directory and click Next.
4. Select “Create a new package group”, use the default settings, and then click Next.
5. Select “Use Lotus Sametime System Console to install” and click Next (see figure 57).

Figure 57. Use Lotus Sametime System Console to install


6. Select to “Use Sametime installed WebSphere Application server” and click Next.
7. Enter the System Console server details and click Validate (see figure 58).

Figure 58. System Console server information


8. Once validated, click Next. Choose the advanced plan you set up, and click Next.
9. Verify your deployment plan and click Next.
10. Click Install to install; click Finish to close the installer.

Installing / setting up standalone Sametime Connect Client

After you have completed the install of all Sametime components in the environment, you are ready to use them in the Sametime Connect Client. Installing and setting up the Connect client is quite straightforward. Here are the steps:

To install:

1. Launch the Connect Client installer, choose the Setup Language, and click OK.
2. Click Next to start installation steps. Accept the license agreement and click Next.
3. Accept the default install location and click Next.
4. Click Install, to begin the installation.

To set up:

1. Before launching the client, you may want to make some changes to the plugin_customization.ini file. The plugin_customization file is located as follows:

2. If you are using an Advanced Server in your environment, add this line to the plugin_customization.ini:

3. Once plugin_customization has been changed, you can launch the Sametime Connect client. You will be prompted for your Community Server name and login credentials. Enter these details and log in.
4. To connect to your Meeting Server, select File – Preferences, expand “Sametime Meeting Rooms,” and click “Meeting Room Servers” (see figure 59).

Figure 59. Meeting Room Servers window



5. Click the Add Meeting Room Server button, and enter the name of your Meeting Server and the port number (9080) (see figure 60).

Figure 60. Add a Meeting Server window


6. Click OK; you should see your Meeting server listed now.
7. Click the Meeting Server tab in the client to confirm your connection to your Meeting Server. It should look like that shown in figure 61.

Figure 61. Sametime Meeting tab



The next step is to add your Advanced Server details:

1. Select File – Preferences, and expand “Chat Rooms and Broadcast Tools.”
2. In the drop-down menu, go to Broadcast Tools Server, add the name of your Advanced Server, and accept the default port (1883); click OK.
3. Back in the left-hand drop-down menu, go to Sametime Advanced Server, and enter the name of your Advanced Server and the port number (9080); click OK. You must restart your client for these changes to take effect.
4. To confirm you are connected to your Advanced Server, the Broadcast Communities and Chat Rooms tab on the Connect client should look like that shown in figure 62.

Figure 62. Broadcast Communities and Chat Rooms tabs

Conclusion

You should now know how to use the Sametime System Console to set up your entire Sametime 8.5.2 environment as either a cell or federated deployment---including the Community Server, Meeting Server, Proxy Server, Media Server, Advanced Server---and how to install and set up your Connect client for use with your environment.

Resources

developerWorks Lotus Sametime product page:
http://www.ibm.com/developerworks/lotus/products/instantmessaging/

Lotus Sametime Forum:
http://www.ibm.com/developerworks/lotus/products/instantmessaging/

Sametime wiki Product Documentation:
http://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Product%20Documentation

IBM Redbooks® publication: “Lotus Sametime Application Development Guide:”
http://www.redbooks.ibm.com/abstracts/SG245651.html?Open

developerWorks WebSphere Application Server zone:
http://www.ibm.com/developerworks/websphere/zones/was/

About the authors

Naveed Yousuf is a Software Engineer working on various teams at IBM's Dublin Software Lab since 1999. He has worked with the Sametime Verification Test team for the past 4 years, focusing on integration and interoperability across IBM Sametime products.

Conall O'Cofaigh is a Software Engineer working on the Sametime Verification Test team. He's been with IBM since 2008, focusing on integration and interoperability across Lotus Sametime products.